home *** CD-ROM | disk | FTP | other *** search
- Path: mail2news.demon.co.uk!genesis.demon.co.uk
- From: Lawrence Kirby <fred@genesis.demon.co.uk>
- Newsgroups: comp.lang.c
- Subject: Re: Why does a compiled program fail on another machine?
- Date: Wed, 03 Jan 96 14:32:21 GMT
- Organization: none
- Message-ID: <820679541snz@genesis.demon.co.uk>
- References: <820634806snz@metsys.demon.co.uk> <30ea6d57.45218688@nntp.ix.netcom.com>
- Reply-To: fred@genesis.demon.co.uk
- X-NNTP-Posting-Host: genesis.demon.co.uk
- X-Newsreader: Demon Internet Simple News v1.27
- X-Mail2News-Path: genesis.demon.co.uk
-
- In article <30ea6d57.45218688@nntp.ix.netcom.com>
- miker3@ix.netcom.com "Mike Rubenstein" writes:
-
- >Most likely this is caused by an uninitialized variable that happens
- >to take on a legal argument value for acos() on one machine but not
- >the other.
-
- It could also be due to a slight difference in the way floating point
- is handled on the 2 systems (which is possible). For instance one system
- might evaluate something to 1.0000000000000000 while the other
- evaluates it to 1.0000000000000001. The first is valid while the second is
- a domain error.
-
- Either way though the problem is in the program itself. Log (or debug)
- the value being passed to acos() and the problem will most likely become
- clear.
-
- --
- -----------------------------------------
- Lawrence Kirby | fred@genesis.demon.co.uk
- Wilts, England | 70734.126@compuserve.com
- -----------------------------------------
-